Skip to content

Instantly share code, notes, and snippets.

@hyeluoh
hyeluoh / model-catalog.json
Created July 14, 2026 02:29
CC Switch issue 参考:Codex 官方完整 model-catalog.json(含 GPT-5.6 ultra 推理档位)
{
"models": [
{
"slug": "gpt-5.6-sol",
"prefer_websockets": false,
"support_verbosity": true,
"default_verbosity": "low",
"apply_patch_tool_type": "freeform",
"web_search_tool_type": "text_and_image",
"input_modalities": [
<!DOCTYPE html>
<html lang="he" dir="rtl">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<title>הלוואה כנגד שעבוד רכב — עד 200,000 ש"ח תוך יום עסקים</title>
<meta name="description" content="רכב משנת 2012 ומעלה? בדיקת זכאות ללא עלות, פריסה עד 100 תשלומים. השאירו פרטים.">
<meta name="theme-color" content="#07080A">
<meta name="robots" content="index,follow">
<meta property="og:type" content="website">

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@tuxfight3r
tuxfight3r / 01.bash_shortcuts_v2.md
Last active August 17, 2026 13:24
Bash keyboard shortcuts

Bash Shortcuts

visual cheetsheet

Moving

command description
ctrl + a Goto BEGINNING of command line
name explain-diff-html
description Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections:

@WildSiphon
WildSiphon / DockerDesktop.yaml
Created July 5, 2025 11:00
Docker Desktop direct download links
4.0.0:
Windows: https://desktop.docker.com/win/main/amd64/67817/Docker%20Desktop%20Installer.exe
Mac with Intel chip: https://desktop.docker.com/mac/main/amd64/67817/Docker.dmg
Mac with Apple chip: https://desktop.docker.com/mac/main/arm64/67817/Docker.dmg
release_date: '2021-08-31'
4.0.1:
Windows: https://desktop.docker.com/win/main/amd64/68347/Docker%20Desktop%20Installer.exe
Mac with Intel chip: https://desktop.docker.com/mac/main/amd64/68347/Docker.dmg
Mac with Apple chip: https://desktop.docker.com/mac/main/arm64/68347/Docker.dmg
release_date: '2021-09-13'
@kibotu
kibotu / prompt-injections.md
Last active August 17, 2026 13:19
Prompt Injection & Jailbreak Techniques — Comprehensive Reference

Prompt Injection & Jailbreak Techniques — Comprehensive Reference

Purpose & scope. A defensive/educational knowledge base cataloguing known prompt-injection and jailbreak patterns, the models/systems they have affected, and the defenses against them. Compiled from primary literature (arXiv papers, vendor disclosures) and security research, June 2026.

How to read this. Every technique lists: how it works, an illustrative structural skeleton (the shape of the attack, not a weaponized payload), the models/systems it was reported against, and its current status. Examples are deliberately defanged. >